Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1056

reference
783-tree-1
name
1056
tree-preservation-order

undefined

783-tpo-1
uprn
address-text
point
POINT (-1.035435 50.862704)
geometry
MULTIPOLYGON (((-1.035364 50.862696,-1.035367 50.862710,-1.035377 50.862723,-1.035393 50.862733,-1.035412 50.862739,-1.035434 50.862742,-1.035456 50.862740,-1.035476 50.862733,-1.035492 50.862724,-1.035502 50.862711,-1.035506 50.862697,-1.035503 50.862683,-1.035493 50.862671,-1.035478 50.862661,-1.035458 50.862654,-1.035436 50.862652,-1.035414 50.862654,-1.035394 50.862660,-1.035378 50.862670,-1.035368 50.862682,-1.035364 50.862696)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL